Update version to 2.2.14 across project files#513
Conversation
- Incremented PraisonAI version from 2.2.13 to 2.2.14 in `pyproject.toml`, `uv.lock`, and all relevant Dockerfiles for consistency. - Ensured minimal changes to existing code while maintaining versioning accuracy across the project.
|
Caution Review failedThe pull request is closed. WalkthroughThis update increments the Changes
Sequence Diagram(s)sequenceDiagram
participant Developer
participant Dockerfile
participant Pip
participant PraisonAI
Developer->>Dockerfile: Build image
Dockerfile->>Pip: Install praisonai==2.2.14
Pip->>PraisonAI: Provide version 2.2.14
PraisonAI-->>Dockerfile: Ready for use
Possibly related PRs
Suggested labels
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (12)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for praisonai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello @MervinPraison, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
Summary of Changes
Hello! Gemini here, providing a summary of this pull request to help everyone quickly understand the changes.
This PR, authored by MervinPraison, is primarily focused on updating the project's version number. As stated in the description, the PraisonAI version is being incremented from 2.2.13 to 2.2.14 across various configuration and build files to ensure consistency throughout the project. The changes are minimal, mainly involving find-and-replace operations for the version string, with a couple of minor related adjustments in test and CLI files.
Highlights
- Version Bump: The core change is updating the PraisonAI project version from
2.2.13to2.2.14in key files likepyproject.toml,uv.lock, and multiple Dockerfiles. - Dockerfile Updates: All relevant Dockerfiles (
docker/Dockerfile,docker/Dockerfile.chat,docker/Dockerfile.dev,docker/Dockerfile.ui) and embedded Dockerfile examples in documentation (docs/api/praisonai/deploy.html,docs/developers/local-development.mdx,docs/ui/chat.mdx,docs/ui/code.mdx,praisonai/deploy.py) have been updated to installpraisonai==2.2.14. - Dependency Lock File Update: The
uv.lockfile, which locks dependencies, has been updated to reflect the new2.2.14version for thepraisonaipackage. - Minor Code Adjustments: A redundant
openai_api_keyentry was removed from the configuration logic inpraisonai/cli.py, and test cases intests/test_agents_playbook.pywere updated withpytest.mark.realmarkers, API key checks for skipping, and a minor change in an assertion string.
Changelog
Click here to see the changelog
- docker/Dockerfile
- Updated the
pip installcommand to specifypraisonai==2.2.14.
- Updated the
- docker/Dockerfile.chat
- Updated the
pip installcommand to specifypraisonai==2.2.14.
- Updated the
- docker/Dockerfile.dev
- Updated the
pip installcommand to specifypraisonai==2.2.14.
- Updated the
- docker/Dockerfile.ui
- Updated the
pip installcommand to specifypraisonai==2.2.14.
- Updated the
- docs/api/praisonai/deploy.html
- Updated the embedded Dockerfile example within the documentation to specify
praisonai==2.2.14.
- Updated the embedded Dockerfile example within the documentation to specify
- docs/developers/local-development.mdx
- Updated the embedded Dockerfile example within the documentation to specify
praisonai==2.2.14.
- Updated the embedded Dockerfile example within the documentation to specify
- docs/ui/chat.mdx
- Updated the embedded Dockerfile example within the documentation to specify
praisonai==2.2.14.
- Updated the embedded Dockerfile example within the documentation to specify
- docs/ui/code.mdx
- Updated the embedded Dockerfile example within the documentation to specify
praisonai==2.2.14.
- Updated the embedded Dockerfile example within the documentation to specify
- praisonai/cli.py
- Removed the redundant
'openai_api_key': api_keyentry from the agent configuration dictionary.
- Removed the redundant
- praisonai/deploy.py
- Updated the generated Dockerfile content within the
create_dockerfilemethod to specifypraisonai==2.2.14.
- Updated the generated Dockerfile content within the
- pyproject.toml
- Updated the
versionfield from2.2.13to2.2.14in the[project]section. - Updated the
versionfield from2.2.13to2.2.14in the[tool.poetry]section.
- Updated the
- tests/test_agents_playbook.py
- Added
pytestandosimports. - Added
@pytest.mark.realdecorator totest_main_with_autogen_framework,test_main_with_custom_framework,test_main_with_internet_search_tool, andtest_main_with_built_in_tool. - Added logic to skip tests if a valid
OPENAI_API_KEYis not found, specifically checking for 'test-key' or 'sk-test-' prefixes. - Changed the assertion string from
'### Task Output ###'to'### Output ###'intest_main_with_autogen_framework.
- Added
- uv.lock
- Updated the version for the
praisonaipackage from2.2.13to2.2.14.
- Updated the version for the
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
A version number climbs,
Through code and Docker rhymes,
From thirteen to fourteen,
A consistent scene,
Across files, in these times.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Code Review
This pull request primarily focuses on updating the PraisonAI version to 2.2.14 across various project files, which has been done consistently. The enhancements to the test suite in tests/test_agents_playbook.py with pytest.mark.real and API key checks are good improvements for testability and CI stability.
However, there are a couple of changes outside the direct version bump that require clarification to ensure they don't introduce regressions or unexpected behavior, particularly concerning AutoGen compatibility and test assertions.
Summary of Findings
- Potential AutoGen Compatibility Issue: Removal of
'openai_api_key'fromconfig_listinpraisonai/cli.pymight affect AutoGen compatibility, as a comment indicated AutoGen sometimes expects this field. This needs verification to prevent potential regressions for users. - Unexplained Test Assertion Change: The expected output string in an AutoGen framework test (
test_main_with_autogen_frameworkintests/test_agents_playbook.py) has changed. The reason for this change needs clarification to ensure test validity and to understand if there's an underlying behavioral change in the library's output for AutoGen.
Merge Readiness
The pull request makes good progress on version consistency. However, before merging, it's important to address the concerns raised about the removal of the openai_api_key field in praisonai/cli.py and the corresponding change in the test assertion for the AutoGen framework. These changes could potentially impact existing users or mask unintended behavior if not thoroughly verified and explained.
I am unable to approve this pull request myself. Please ensure these points are clarified and potentially further reviewed by others familiar with AutoGen integration before merging.
| 'model': os.environ.get("OPENAI_MODEL_NAME", "gpt-4o"), | ||
| 'base_url': os.environ.get("OPENAI_API_BASE", "https://api.openai.com/v1"), | ||
| 'api_key': api_key, | ||
| 'openai_api_key': api_key, # AutoGen sometimes expects this field name |
There was a problem hiding this comment.
The line 'openai_api_key': api_key, # AutoGen sometimes expects this field name was removed. The comment suggests this key might be important for AutoGen compatibility.
Could you clarify the reason for this removal?
- Has it been confirmed that AutoGen (across various versions or configurations it might be used with PraisonAI) no longer requires or benefits from this specific
openai_api_keyfield, and that the existingapi_keyfield is now universally sufficient? - Was this change tested to ensure no regressions for users integrating with AutoGen, especially those who might have relied on this specific key name?
Given the PR's focus on versioning, this change seems out of scope unless it's a necessary cleanup tied to version 2.2.14. Ensuring backward compatibility or clearly documenting such breaking changes is important.
| try: | ||
| result = praisonai.run() | ||
| self.assertIn('### Task Output ###', result) | ||
| self.assertIn('### Output ###', result) |
There was a problem hiding this comment.
The assertion in test_main_with_autogen_framework has changed from looking for ### Task Output ### to ### Output ###.
What prompted this change in the expected output string for the AutoGen framework test?
- Is this due to a deliberate change in the output format of
praisonai.run()in version 2.2.14? - Or is it possibly related to the removal of the
openai_api_keyinpraisonai/cli.pyaffecting AutoGen's output?
Understanding the reason for this change is important to ensure the test is still correctly verifying the intended behavior and not masking an unintended side-effect.
Update version to 2.2.14 across project files
1 participant
pyproject.toml,uv.lock, and all relevant Dockerfiles for consistency.Summary by CodeRabbit
Chores
Bug Fixes
Tests